Skip to content

Conversation

@avinashbot
Copy link
Member

@avinashbot avinashbot commented Apr 28, 2025

Description

Based on further discussion with the accessibility specialists, this seemed to be the best way to go. We already have a tabular structure, so it makes sense for it to be navigable as a table as well (plus, tables are just easy to navigate). That visual change is intentional; it previously started with "This is line number 2" on the first line.

Code view (also other side packages) doesn't have support for I18nProvider, so this won't enable itself unless the strings are completely provided. They should support I18nProvider, of course, but that's a matter for a different time.

Related links, issue #, if available: AWSUI-60236

How has this been tested?

Updated unit tests, tested on VoiceOver and NVDA manually as well. But try it out yourself! Enable VoiceOver, enter the table, and use VO+Arrow Keys. (VO = Control + Option).

Review checklist

The following items are to be evaluated by the author(s) and the reviewer(s).

Correctness

  • Changes include appropriate documentation updates.
  • Changes are backward-compatible if not indicated, see CONTRIBUTING.md.
  • Changes do not include unsupported browser features, see CONTRIBUTING.md.
  • Changes were manually tested for accessibility, see accessibility guidelines.

Testing

  • Changes are covered with new/existing unit tests?
  • Changes are covered with new/existing integration tests?

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@codecov
Copy link

codecov bot commented Apr 28, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.28%. Comparing base (271e3cf) to head (12b1819).
Report is 5 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #78      +/-   ##
==========================================
+ Coverage   99.23%   99.28%   +0.05%     
==========================================
  Files          29       29              
  Lines         260      280      +20     
  Branches       31       34       +3     
==========================================
+ Hits          258      278      +20     
  Misses          1        1              
  Partials        1        1              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@avinashbot avinashbot changed the title experiment: Use semantic table to show line numbers to assistive technology fix: Use semantic table to show line numbers to assistive technology May 12, 2025
@avinashbot avinashbot force-pushed the fix-line-numbers-a11y branch from f922ff1 to 5da7710 Compare May 15, 2025 09:41
@avinashbot avinashbot marked this pull request as ready for review May 15, 2025 10:27
@avinashbot avinashbot requested a review from a team as a code owner May 15, 2025 10:27
@avinashbot avinashbot requested review from jperals and removed request for a team May 15, 2025 10:27
@jperals
Copy link
Member

jperals commented May 15, 2025

What if one of the two new strings is defined but not the other? Do we want to issue console warnings?

@avinashbot
Copy link
Member Author

@jperals I did think about console warnings, but I wanted to be a bit cautious for now - I want to look into I18nProvider support as a follow up, and so I didn't want to pull in our special dev-only warnOnce function into the bundle for something most people might not have to think about.

@avinashbot avinashbot requested a review from jperals May 15, 2025 10:45
jperals
jperals previously approved these changes May 15, 2025
@avinashbot
Copy link
Member Author

avinashbot commented May 15, 2025

@jperals Ah, you're right about the strings. Let me add some docs there.

@avinashbot avinashbot added this pull request to the merge queue May 15, 2025
Merged via the queue into main with commit 5ef2c97 May 15, 2025
38 of 39 checks passed
@avinashbot avinashbot deleted the fix-line-numbers-a11y branch May 15, 2025 12:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants